Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1393

reference: 626-tree-1
name: 1393
tree-preservation-order: undefined
626-tpo-1
uprn
address-text
point: POINT (-1.023171 50.880944)
geometry: MULTIPOLYGON (((-1.023100 50.880937,-1.023103 50.880950,-1.023113 50.880963,-1.023128 50.880973,-1.023148 50.880980,-1.023170 50.880982,-1.023192 50.880980,-1.023212 50.880974,-1.023228 50.880964,-1.023238 50.880952,-1.023242 50.880938,-1.023239 50.880924,-1.023229 50.880911,-1.023213 50.880901,-1.023194 50.880895,-1.023172 50.880892,-1.023150 50.880894,-1.023130 50.880900,-1.023114 50.880910,-1.023104 50.880923,-1.023100 50.880937)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL